#21582 [BUG][dart-dio] Bug generating inline enums with common names#21591
#21582 [BUG][dart-dio] Bug generating inline enums with common names#21591wing328 merged 8 commits intoOpenAPITools:masterfrom
Conversation
…ommon names added petstore test
|
thanks for the pr. please follow step 3 to update the samples when you've time to fix https://github.com/OpenAPITools/openapi-generator/actions/runs/16381888238/job/46309975996?pr=21591 |
…ommon names added generated samples to commit.
|
Thanks @wing328 I have updated and it includes the generated files this time. |
| @@ -0,0 +1,8 @@ | |||
| generatorName: dart-dio | |||
| outputDir: samples/openapi3/client/bug-samples/issue_21582 | |||
| inputSpec: modules/openapi-generator/src/test/resources/bugs/issues_21582.yaml | |||
There was a problem hiding this comment.
given that you've added the test schemas to dart petstore fake spec file, i don't think we need this yaml config and the new test spec for this particular issue: modules/openapi-generator/src/test/resources/bugs/issues_21582.yaml
There was a problem hiding this comment.
Thanks @wing328 , I wasn't sure what the preferred convention was. I have removed the content and the generated files and updated.
…ommon names removed bug test files that were duplicates
|
@wing328 do I need to do anything else before progressing the workflow? |
please add the new files and update the samples again |
…ommon names. Added generated files that were missed.
…ommon names. Added generated files that were missed.
…ommon names. Added generated files that where updated as a result of changes in master.
|
thanks again for the pr i did a test with the spec provided in #21582 but got errors when running did you get similar errors locally in your machine? command to generate the dart package for testing: |
|
@wing328 did you run |
|
that fixes it. i'm now able to repeat the issue and confirm the fix. thanks for the PR if users prefer the old way of naming the enum, we will then provide an option for fallback. |
…ommon names (OpenAPITools#21591) * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names added petstore test * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names added generated samples to commit. * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names removed bug test files that were duplicates * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names. Added generated files that were missed. * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names. Added generated files that were missed. * OpenAPITools#21582 [BUG][dart-dio] Bug generating inline enums with common names. Added generated files that where updated as a result of changes in master.
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming7.x.0minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)This pull request is a fix for #21582
fix #21582
I wasn't sure what the best convention was for creating integration tests I first created it in the
test\resources\bugsfolder but then after rereading the contribution guidelines created updated the petstore test inmodules/openapi-generator/src/test/resources/3_0/dart/petstore-with-fake-endpoints-models-for-testing.yamlTechnical committee mentions
@jaumard @josh-burton @amondnet @sbu-WBT @kuhnroyal @agilob @ahmednfwela